Industrial vehicle geo-feature system

ABSTRACT

When an industrial vehicle encounters a geo-feature, one or more messages for conveyance on the industrial vehicle are determined based on a current operating state of the industrial vehicle and an expected operating condition associated with the encountered geo-feature. In an example implementation, the geo-feature can implement aisle control in a warehouse or similar environment to ensure that only authorized vehicles are permitted to enter the aisle. Here, authorization may be predicated upon an assigned task from a warehouse management system. In another example implementation, the industrial vehicle includes a display that provides a graphical representation of the geo-feature.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/140,943, filed Sep. 25, 2018, entitled INDUSTRIAL VEHICLE GEO-FEATURESYSTEM, now allowed, which is a continuation of U.S. patent applicationSer. No. 15/162,723, filed May 24, 2016, entitled INDUSTRIAL VEHICLEGEO-FEATURE SYSTEM, issued as U.S. Pat. No. 10,086,756, which claims thebenefit of U.S. Provisional Patent Application Ser. No. 62/166,082,filed May 25, 2015, entitled INDUSTRIAL VEHICLE GEO-FEATURE SYSTEM, thedisclosures of which are hereby incorporated herein by reference.

BACKGROUND

The present disclosure relates to electronic systems for collectinginformation related to the operation of industrial vehicles, and inparticular to the integration and manipulation of such information withgeo-features.

Wireless strategies are being deployed by business operations, includingdistributors, retail stores, manufacturers, etc., to improve theefficiency and accuracy of business operations. Wireless strategies mayalso be deployed by such business operations to avoid the insidiouseffects of constantly increasing labor and logistics costs.

In a typical wireless implementation, workers are linked to a managementsystem executing on a corresponding computer enterprise via mobilewireless transceivers. The wireless transceivers are used as interfacesto the management system to direct workers in their tasks, e.g., byinstructing workers where and/or how to pick, pack, put away, move,stage, process or otherwise manipulate the items within a facility. Thewireless transceiver may also be used in conjunction with a suitableinput device to scan, sense or otherwise read tags, labels or otheridentifiers to track the movement of designated items within thefacility.

BRIEF SUMMARY

According to aspects of the present disclosure, a machine-executableprocess in an industrial vehicle environment is provided. The processcomprises electronically receiving by a processor on an industrialvehicle, geo-feature information about a geo-feature that is located inan area upon which the industrial vehicle travels. The process alsocomprises detecting that the industrial vehicle has encountered thegeo-feature. Moreover, the process comprises generating by theprocessor, an output message in response to detecting that theindustrial vehicle has encountered the geo-feature. Here, the outputmessage comprises a select one of a first message where a currentoperating state of the industrial vehicle is within a designatedacceptable range of an expected operating state, and a second messagedifferent from the first message, where the current operating state isoutside the designated acceptable range of the expected operating state.The process yet further comprises conveying the output message on theindustrial vehicle.

According to further aspects of the present disclosure, amachine-executable process in an industrial vehicle environment isprovided. The process comprises detecting that an industrial vehicle hasencountered a geo-feature designated as an aisle restriction zone. Theprocess also comprises performing, upon detecting that the industrialvehicle has encountered the geo-feature a set of operations. The set ofoperations comprise extracting from a warehouse management systemcomputer, task information indicating whether the industrial vehicle isassigned a task to maneuver a load in an aisle associated with the aislerestriction zone. The set of operations also comprises generating acommand that controls the industrial vehicle. The command comprises aselect one of a first command that restricts the industrial vehicle fromentering the aisle where the industrial vehicle is not assigned a taskto maneuver a load in the aisle, and a second command that enables theindustrial vehicle to enter the aisle where the industrial vehicle isassigned a task to maneuver a load in the aisle.

According to still further aspects of the present disclosure, amachine-executable process in an industrial vehicle environment isprovided. The process comprises obtaining geo-feature information aboutgeo-features that are located in an area upon which an industrialvehicle travels. The process also comprises outputting to a display onthe industrial vehicle, a view that represents the area upon which theindustrial vehicle is traveling. Moreover, the process comprisesvisually indicating on the display, a location of detected geo-featureswithin the view of the display. The process still further comprisesdetecting that the industrial vehicle has encountered a selectgeo-feature. Yet further, the process comprises performing, upondetecting that the industrial vehicle has encountered the selectgeo-feature, a corresponding action on the industrial vehicle, where thecorresponding action is determined based upon the identity of the selectgeo-feature.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 is a block diagram of a system that includes geo-features,according to aspects of the disclosure;

FIG. 2 is a block diagram of a special purpose processing device on anindustrial vehicle, which is capable of implementing geo-featureprocessing according to aspects of the present disclosure herein;

FIG. 3 illustrates a graphical user interface executing on a tabletcomputer that is specifically configured for setting up geo-featureswithin a bounded environment, such as a warehouse, according to aspectsof the present disclosure herein;

FIG. 4A is the graphical user interface of FIG. 3 illustrating thecreation of geo-features, according to aspects of the present disclosureherein;

FIG. 4B is the graphical user interface of FIG. 3 illustrating thecreation of layers of geo-features, according to aspects of the presentdisclosure herein;

FIG. 4C is the graphical user interface of FIG. 3 illustrating thecreation of events, according to aspects of the present disclosureherein;

FIG. 4D is the graphical user interface of FIG. 3 illustrating theability to identify areas where events and/or geo-features triggered thegeneration of an event record, according to aspects of the presentdisclosure herein;

FIG. 4E is the graphical user interface of FIG. 3 illustrating abilityto set a priority in case of conflicting geo-features and/or events,according to aspects of the present disclosure herein;

FIG. 5 is a flow chart of a process for creating geo-features accordingto aspects of the present disclosure herein;

FIGS. 6A-6C illustrates an industrial vehicle improperly travelingthrough an intersection containing a geo-feature implemented as a stopzone, where the industrial vehicle travels through the geo-featurewithout stopping;

FIGS. 6D-6G illustrates a graphical user interface that is re-playing arecorded event of the industrial vehicle of FIGS. 6A-6C where anindustrial vehicle encounters a geo-feature, according to aspects of thepresent disclosure herein;

FIG. 7A is a flow chart illustrating a process for displaying a messageon an industrial vehicle, according to various aspects of the presentdisclosure;

FIG. 7B illustrates a particular flow for carrying out the generation ofoutput at 708 of FIG. 7A;

FIG. 8 is an illustration showing an example of the process fordisplaying a message on an industrial vehicle, according to variousaspects of the present disclosure;

FIG. 9 is an illustration showing another example of the process fordisplaying a message on an industrial vehicle, according to variousaspects of the present disclosure;

FIG. 10 is an illustration showing yet another example of the processfor displaying a message on an industrial vehicle, according to variousaspects of the present disclosure;

FIG. 11 is a flow chart illustrating a vehicle based event generationapproach, according to aspects of the present disclosure; and

FIG. 12 is a block diagram of a computer processing system capable ofimplementing any of the systems, processes (or subsets thereof)described more fully herein.

DETAILED DESCRIPTION

According to various aspects of the present disclosure, systems, andcomputer implemented processes are provided, which collect and blendindustrial vehicle operational information with dynamic, virtualgeo-feature information such that the virtual geo-feature informationimpacts, augments, or otherwise integrates with, real-world industrialvehicle activity within a working environment. Accordingly, thedisclosure herein improves the technology of industrial vehicleoperation, control and communication. Moreover, disclosure hereinimproves the technology of real-time position and operation monitoring,tracking and control.

In general terms, geo-features are used for processing location-basedevents. Also, geo-features are used for processing vehicle-based events.In this regard, tools are provided that enable a user (e.g., a manager,supervisor) to interact with a graphical user interface to define,create, manipulate, etc., geo-features, events, and other elements thataffect a fleet of industrial vehicles. The graphical user interface canbe executed on any processing device, such as on a tablet, smart phoneor other hand-held processing device, laptop, desktop, etc. In anexemplary implementation of setting up location-based geo-features, thegraphical user interface displays a model that represents a bounded orotherwise limited physical environment such as a warehouse. In a typicalinstance, the model shows a warehouse, including features such as racklocations, travel aisles, travel lanes, loading and unloading areas,etc. The user identifies geo-features, such as by drawing out geo-zonesdirectly onto the model. The user may also (or alternatively) definegeo-features by entering information in response to prompts issuedthrough the graphical user interface. The user then generatesgeo-feature information, such as by assigning parameter(s) to thecreated geo-features to define a programmed action in response to anencounter with the created geo-feature.

For vehicle-based events, the user utilizes the graphical user interfaceto define events (event descriptions), where an event descriptioncharacterizes an event related to an operation that is being carried outon the industrial vehicle. Here, the user defines the conditions of theevent description (including dynamic variables) and a response to anoccurrence to the event.

The information created on the graphical user interface is wirelesslyloaded into industrial vehicles that operate in the physical environmentrepresented by the model. As such, the industrial vehicles are speciallyprogrammed to respond to the created geo-features, programmed eventdescriptions, or combinations thereof. Thus for instance, during normaloperation, when a programmed industrial vehicle encounters ageo-feature, an event is triggered that causes corresponding programmedaction to occur on the industrial vehicle.

System Overview:

Referring now to the drawings and in particular to FIG. 1, a generaldiagram of a computer system 100 is illustrated according to variousaspects of the present disclosure. The illustrated computer system 100is a special purpose (particular) system that operates usinggeo-features, event descriptions, or combinations thereof, as set out ingreater detail herein. The computer system 100 comprises a plurality ofhardware processing devices (designated generally by the reference 102)that are linked together by one or more network(s) (designated generallyby the reference 104).

The network(s) 104 provides communications links between the variousprocessing devices 102 and may be supported by networking components 106that interconnect the processing devices 102, including for example,routers, hubs, firewalls, network interfaces, wired or wirelesscommunications links and corresponding interconnections, cellularstations and corresponding cellular conversion technologies (e.g., toconvert between cellular and TCP/IP, etc.). Moreover, the network(s) 104may comprise connections using one or more intranets, extranets, localarea networks (LAN), wide area networks (WAN), wireless networks (WiFi),the Internet, including the world wide web, cellular and/or otherarrangements for enabling communication between the processing devices102, in either real time or otherwise (e.g., via time shifting, batchprocessing, etc.).

A processing device 102 can be implemented as a transactional system,purpose-driven appliance, special purpose computing device and/or otherdevice capable of communicating over the network 104. Other types ofprocessing devices 102 include for example, personal data assistant(PDA) processors, palm computers, cellular devices including cellularmobile telephones and smart telephones and tablet computers. Theprocessing devices 102 can also comprise netbook computers, notebookcomputers, personal computers and servers.

In certain contexts and roles, a processing device 102 is intended to bemobile (e.g., a processing device 102 provided on an industrial vehicle108 such as a forklift truck, reach truck, stock picker, turret truck,tow tractor, rider pallet truck, walkie stacker truck, etc.). In thisregard, industrial vehicles include a particular processing device 102that communicates wirelessly to the network 104. Under suchcircumstances, the industrial vehicles 108 can wirelessly communicatethrough one or more access points 110 to a corresponding networkingcomponent 106. Alternatively, the industrial vehicles 108 can beequipped with WiFi, cellular or other suitable technology that allowsthe processing device 102 on the industrial vehicle 108 to communicatedirectly with a remote device (e.g., over the networks 104).

The illustrative computer system 100 also includes a server 112 (e.g., aweb server, file server, and/or other processing device) that supportsan analysis engine 114 and corresponding data sources (collectivelyidentified as data sources 116). The analysis engine 114 and datasources 116 provide the resources to implement and store data related togeo-features and encounters with geo-features, captured events,combinations thereof, etc., as described in greater detail herein.

In an exemplary implementation, the data sources 116 are implemented bya collection of databases that store various types of informationrelated to a business operation (e.g., a warehouse, distribution center,retail store, manufacturer, etc.). However, these data sources 116 neednot be co-located. In the illustrative example, the data sources 116include databases that tie processes executing for the benefit of theenterprise, from multiple, different domains. In the illustratedexample, data sources 116 include an industrial vehicle informationdatabase 118 (supporting processes executing in an industrial vehicleoperation domain), a warehouse management system (WMS) 120 (supportingprocesses executing in WMS domain that relate to movement and trackingof goods within the operating environment), a human resources managementsystem (HRMS) 122 (supporting processes executing in an HRMS domain), alabor management system (LMS) 124 (supporting processes executing in anLMS domain), etc.

The above list is not exhaustive and is intended to be illustrativeonly. Other data, such as from an enterprise resources planning (ERP)database, content management (CM) database, location tracking database,voice recognition data source (for electronically receiving voicecommands from an operator), voice command/messaging system (forelectronically conveying voice commands to the operator), and theircorresponding domain processes etc., may also and/or alternatively bepresent. Moreover, data can come from sources that are not directlyand/or locally connected to the analysis engine 114. For instance, incertain exemplary implementations, data may be obtained from remoteservers (e.g., to access manufacturer databases, etc.).

Industrial Vehicle:

As noted above, in certain contexts and roles, a processing device 102is provided on an industrial vehicle 108. Here, the processing device102 is a special purpose, particular computer, such as a device thatmounts to or is otherwise integrated with the industrial vehicle 108.The processing device 102 includes a processor coupled to memory tocarry out instructions. However, the execution environment of theprocessing device 102 is further tied into the industrial vehicle 108making it a particular machine different from a general purposecomputer.

For instance, an example computing device 102 on an industrial vehicleis a mobile asset information linking device (see information linkingdevice 38) as set out in U.S. Pat. No. 8,060,400, the disclosure ofwhich is incorporated by reference in its entirety. In certainillustrative implementations, the processing device 102 alsocommunicates with components of the corresponding industrial vehicle 108(e.g., via a vehicle network bus (e.g., CAN bus), short range wirelesstechnology (e.g., via Bluetooth or other suitable approach), or otherwired connection, examples of which are set out further in U.S. Pat. No.8,060,400, already incorporated by reference.

Referring to FIG. 2, a processing device 102 is implemented as aninformation linking device that comprises the necessary circuitry toimplement wireless communication, data and information processing, andwired (and optionally wireless) communication to components of theindustrial vehicle. As a few illustrative examples, the processingdevice 102 includes a transceiver 202 for wireless communication.Although a single transceiver 202 is illustrated for convenience, inpractice, one or more wireless communication technologies may beprovided. For instance, the transceiver 202 may be able to communicatewith a remote server, e.g., server 112 and hence, interact with theanalysis engine 114 of FIG. 1, via 802.11.xx across the access points110 of FIG. 1. The transceiver 202 may also optionally support otherwireless communication, such as cellular, Bluetooth, infrared (IR) orany other technology or combination of technologies. For instance, usinga cellular to IP bridge, the transceiver 202 may be able to use acellular signal to communicate directly with a remote server, e.g., amanufacturer server.

The processing device 102 also comprises a control module 204, having aprocessor coupled to memory for implementing computer instructions,including the relevant processes, or aspects thereof, e.g., as set outand described more fully herein with reference to FIGS. 3-11. In thisregard, the processor of the control module 204 can interact with theanalysis engine 114 (FIG. 1) in carrying out one or more featuresdescribed herein with reference to FIGS. 3-11. Additionally, the controlmodule 204 implements processes such as operator log on, pre-useinspection checklists, data monitoring and other features, examples ofwhich are described more fully in U.S. Pat. No. 8,060,400 to Wellman,already incorporated by reference herein.

The processing device 102 further includes vehicle power enablingcircuitry 206 to selectively enable or disable the industrial vehicle108. In certain implementations, the vehicle power enabling circuitry206 can partially enable the industrial vehicle 108 for operation, orfully enable the industrial vehicle 108 for operation, e.g., dependingupon proper operator login. For instance, the industrial vehicle powerenabling circuitry 206 can provide selective power to components viapower line 208. Also, the industrial vehicle power enabling circuitry206 may be utilized by geo-features to control access to an industrialvehicle 108, e.g., to perform vehicle lock-out for violating a warehouseprocedure, such as sitting idle too long in a designated area.

Still further, the processing device 102 includes a monitoring inputoutput (I/O) module 210 to communicate via wired or wireless connectionto peripheral devices mounted to or otherwise on the industrial vehicle,such as sensors, meters, encoders, switches, etc. (collectivelyrepresented by reference numeral 212). The processing device 102 mayalso be connected to other devices, e.g., third party devices 213 suchas RFID scanners, displays, meters or other devices.

The processing device 102 is coupled to and/or communicates with otherindustrial vehicle system components via a suitable industrial vehiclenetwork system 214, e.g., a vehicle network bus. The industrial vehiclenetwork system 214 is any wired or wireless network, bus or othercommunications capability that allows electronic components of theindustrial vehicle 108 to communicate with each other. As an example,the industrial vehicle network system may comprise a controller areanetwork (CAN) bus, ZigBee, Bluetooth, Local Interconnect Network (LIN),time-triggered data-bus protocol (TTP) or other suitable communicationstrategy.

As will be described more fully herein, utilization of the industrialvehicle network system 214 enables seamless integration of thecomponents of the processing device 102 on the industrial vehicle 108into the native electronics including controllers of the industrialvehicle 108. Moreover, the monitoring I/O 210 can bridge any electronicperipheral devices 212 to the industrial vehicle network system 214. Forinstance, as illustrated, the processing device 102 connects with,understands and is capable of communication with native vehiclecomponents, such as controllers, modules, devices, bus enabled sensors,displays, lights, light bars, sound generating devices, headsets,microphones, haptic devices, etc. (collectively referred to by reference216).

The processing device 102 can also communicate with a FOB 218 (orkeypad, card reader or any other device) for receiving operator log inidentification. Still further, the processing device 102 can include adisplay and/or other features to provide desired processing capability.

According to yet further aspects of the present disclosure, anenvironmental based location tracking device 220 may be provided on theindustrial vehicle 108, which can communicate across the industrialvehicle network system 214. The environmental based location trackingdevice 220 enables the industrial vehicle 108 to be spatially aware ofits location within the warehouse. The environmental based locationtracking device 220 can comprise a local awareness system that utilizesmarkers, including RFID, beacons, lights, or other external devices toallow spatial awareness within the warehouse environment. Theenvironmental based location tracking system 220 may use one or more ofa global positioning system (GPS), or triangulation system to determineposition. The environmental based location tracking system 220 may alsouse knowledge read from vehicle sensors, encoders, accelerometers, etc.,or other system that allows location to be determined. As a furtherexample, the environmental based location tracking system 220 mayinclude a transponder, and the position of the industrial vehicle may betriangulated within the facility. Yet further, the environmental basedlocation tracking system 220 may use combinations of the above and/orother technologies to determine the current (real-time) position of theindustrial vehicle. As such, the position of the industrial vehicle canbe continuously ascertained (e.g., every second or less) in certainimplementations. Alternatively, other sampling intervals can be derivedto continuously (e.g., at discrete defined time intervals, periodic orotherwise constant and recurring time intervals, intervals based uponinterrupts, triggers or other measures) determine industrial vehicleposition over time.

Geo-Feature Creation:

According to various aspects of the present disclosure, geo-features arecreated in a virtual environment, and are deployed in a correspondingphysical environment where industrial vehicles operate. As will bedescribed in greater detail herein, geo-features are features that arecreated and administered through an electronic means. In certainimplementations, the geo-features are defined by a graphical userinterface in a virtual environment that resembles or otherwiserepresents the actual environment in which the industrial vehiclesoperate. The virtualization aspect of a virtual environment is notrequired, but is convenient for the user setting up the geo-features.Alternatively, geo-features can be created using command prompts orother programming techniques. In certain implementations, thegeo-features can be set up, taken down, or otherwise modified in anad-hoc manner. Moreover, geo-features are not purely limited to spatialposition. Rather, geo-features may be enabled or disabled based upon thetype of industrial vehicle, the operator, the time of day, operatingconditions of an industrial vehicle encountering the geo-feature, thestate of processes in various warehouse operational domains, or basedupon other factors, examples of which are set out in greater detailherein.

Referring now to FIG. 3, a processing device 102 is illustrated, whichcan be utilized with any of the components and configurations describedwith regard to FIG. 1. The processing device 102 is illustrated in theform factor of a physical, hardware tablet computer 302, and isimplemented as a hardware computing device configured to executecomputer code to generate a graphical user interface 304 for interactingwith industrial vehicles.

The graphical user interface 304 presents a model 306 depicting agraphical representation of a virtual environment that corresponds to aphysical environment, where the physical environment is contained withina bounded or otherwise limited physical environment, such as awarehouse. In this regard, a typical warehouse is a large building thatincludes rows of racking. Each row of racking typically includes severalvertically spaced rows of bins, each bin holding one or more pallets.Goods that are stored in the warehouse are typically loaded onto thepallets and are thus temporarily stored in the bins. Warehouses alsotypically include travel aisles or lanes for industrial vehicles (e.g.,forklifts) to navigate in order to place and retrieve pallets incorresponding bins. Warehouses also typically include lanes designatedfor shipping, receiving, inspection, or other purposes. Yet further,warehouses may have designated regions that are intended for limitedaccess, e.g., for storing bonded goods, for storing goods that needrefrigeration, break rooms, sorting areas, packing areas, maintenanceareas, etc. The above features of a typical warehouse are not meant tobe exhaustive, and other features may be present in an actualimplementation.

As such, the model 306 may be a two-dimensional map of the warehouse, orthe model 306 may be a three-dimensional model of the warehouse, e.g.,to properly map not only the floor plan of the warehouse, but also toaccount for racking, height, doorways, rooms, and otherthree-dimensional features within the warehouse.

In a simplified example for sake of discussion herein, the model 306depicts rows of racking 308A, 308B, 308C, 308D. A first aisle 310Aextends between racking 308A and 308B. A second travel aisle 310Bextends between racking 308B and 308C. A third travel aisle 310C extendsbetween 308C and 310D, etc. Of course, in practice, the model 306 cansupport any structures that are present in the real correspondingwarehouse, and thus the model 306 is not limited to racking 308 andaisles 310. Moreover, for each modeled element, data may be recorded,such as X, Y, Z coordinates, dimensions, etc. Still further, menu items312 may be provided to launch dialog boxes to collect data about thedefinition of the model 306, of created geo-features, etc.

Location-Based Setup:

Referring to FIG. 4A, the hardware tablet computer 302 executes thegraphical user interface 304 to provide a tool that enables a user todefine a geo-feature 402 at a location on the model 306. A geo-feature402 is not limited to pure fixed spatial positioning however. Forinstance, a geo-feature 402 can be drawn around a virtual industrialvehicle or other virtual movable warehouse component corresponding to anactual industrial vehicle 108 or other actual movable warehousecomponent, as will be described in greater detail herein. Notablyhowever, many types of geo-features 402 are location dependent.

Accordingly, as used herein, a geo-feature 402 can correspond to anelement, zone, location, event, or other definable element within thevirtual environment. In the example implementation, the geo-featuretransforms into an industrial vehicle control in the correspondingphysical environment such that an event triggers a corresponding actionon an industrial vehicle 108 within the corresponding physicalenvironment when the industrial vehicle 108 encounters the geo-feature402, as will be described in greater detail herein.

As used herein, an industrial vehicle control is a signal processed byan industrial vehicle 108 in response to encountering a geo-feature. Theindustrial vehicle 108 can receive the signal, such as via a wirelesstransmission from a server (e.g., server 112 of FIG. 1) or other source.The industrial vehicle 108 can alternatively generate the signal, suchas where geo-feature detection is carried out locally on the industrialvehicle itself, such as by using an environmental based locationtracking system 220. Regardless, the industrial vehicle control carriedout in response to the signal may be in the form of an alert, e.g., byinitiating a light, display, prompt with a textual message, sound,speech based audible message, haptic response, combination thereof, etc.The industrial vehicle control may also take the form of an operationalcontrol, e.g., to perform an automation or other operational function.Still further, the industrial vehicle control may be in the form of amodification to a vehicle operational parameter, e.g., to set a speedlimit, force a travel direction, limit the maximum fork height, etc.,examples of which are set out in greater detail herein.

To facilitate customization of geo-features 402, the graphical userinterface 304 opens a dialog box 404 that enables the user to entergeo-feature information. The geo-feature information encompassesinformation necessary to electronically characterize the geo-feature402. (The dialog box 404 can also optionally be selected from the menu312).

For instance, as illustrated, the geo-feature information is collectedas a set of properties. The properties can include a parameter (orparameters) that defines (define) at least a function, characteristic,or action of the defined geo-feature. The nature of the specificgeo-feature will dictate the geo-feature information.

However, as a few illustrative examples, a parameter may comprisecoordinates of the geo-feature 402 or other data indicating the spatiallocation of the geo-feature 402 (in two-dimensions or three-dimensions).A parameter may also be used to specify the type of geo-feature 402. Byway of example, a geo-feature 402 may be a geo-zone. Moreover, thegeo-zone may be designated as a restriction zone, speed zone, controlzone, height restrict zone, stop zone, horn zone, prompt zone,combination thereof, etc.

Other geo-features 402 can include for instance, a geo-featurerepresenting a zone with lights switched on; a geo-feature pertaining toa requirement for vehicles to yield to vehicles having a right-of-way; ageo-feature for detecting a vehicle passing at a moderate or aggressivespeed; and a geo-feature for detecting proximity areas or detectingavoidances that are near misses.

Yet further, geo-features 402 may also be productivity based. Forinstance, a geo-feature 402 can be based upon a target number of palletsor cases moved; a distance and route target per pick; a target perspecific travel segment; a target per specific lift segment; a targetper specific idle segment; a target for the operator being off thevehicle (e.g., time spent for picking, breaks, etc.); accuracy ofcorrect pick or put location; efficiency of ideal travel distance perpick; excessive over-control of vehicle features; selection of thecorrect battery for the industrial vehicle; selection of the correctbattery charger, proper queue—entering the battery queue; identifying alocation of fuel run-out for internal combustion engine vehicles, etc.

As such, properties 404 are used to define the type of zone and functionthereof. Still further, the properties 404 may include a parameter thatdefines the desired event that triggers recognition of the geo-feature402, e.g., the detection of an industrial vehicle 108 entering a zonemay be an event trigger. Other properties 404, such as leaving a zone,stopping in the zone, not stopping in the zone, vehicle condition oroperating state, raising or lowering the forks in the zone, otherbehaviors, etc., can all define events that can be captured in theproperties 404. Still further, a property 404 may comprise a controlthat is to be programmed into the industrial vehicle 108 when thegeo-feature is encountered (such as set maximum speed to X miles perhour; set maximum fork height to Y inches to accommodate a low header ina doorway; etc.)

The properties 404 can also include parameters defined by logic,including rules, conditions, expressions, algorithms, state machines,etc., to account for dynamic conditions, static conditions, etc.

Another example type of property 404 includes a desired message or suiteof messages that is/are communicated to the industrial vehicle 108 thatencounters the geo-feature 402. For example, a parameter may include apositive reinforcement message if the correct operation is carried outin response to the geo-feature 402, and/or a negative reinforcementmessage if the incorrect operation is carried out in response toencountering the geo-feature 402. Thus, geo-feature information includeselectronic information that encodes a desired outcome in response to thegeo-feature 402. If that desired outcome is observed, then the positivereinforcement message is provided to the industrial vehicle 108 forconveyance at some time after the encounter with the geo-feature 402,otherwise the negative reinforcement message is provided at some timeafter the encounter with the geo-feature 402.

As another example, a geo-feature 402 such as a restriction zone may bedrawn around a loading dock, and configured via the properties 404 so asto apply to turret stock pickers, but not for a designated loading docksit down counterbalance forklift trucks. As such, a turret stock pickermay encounter this geo-feature 402. However, the geo-feature 402 willnot manifest itself to a counterbalance forklift truck that is supposedto be on the loading dock. Thus, geo-feature information can includerules, inclusions, exclusions, etc., to render the geo-feature 402available to only select instances of industrial vehicles 108 capable ofdetecting the corresponding geo-feature 402. Moreover, the conditionsand/or exceptions may be based upon information not directly related tothe industrial vehicle 108, e.g., operator logged onto the industrialvehicle 108, time of day, shift, volume of detected or otherwiseobserved congestion, etc.

As another non-limiting example, geo-feature information in the form ofproperties 404 can be set for a geo-zone 402 such as a restriction zonedrawn around bonded warehouse, but only for operators that log into anindustrial vehicle 108 with improper clearance or credentials for thebonded area defined by the geo-zone.

As additional examples, a geo-feature 402 may be drawn as a restrictionzone for all industrial vehicles except for vehicles having picks in thecorresponding aisle based upon data in the WMS domain. For instance, theprocessor in the control module 204 of a select industrial vehicle 108(FIG. 2) can interact with the analysis engine 114 of the server 112 toextract pick information from the WMS data 120 (FIG. 1), which is usedto judge whether a geo-feature 402 is applicable.

As still other examples, a geo-feature 402 such as a prompt zone mayonly prompt an industrial vehicle 108 to slow down if the industrialvehicle 108 is traveling above a predetermined maximum speed in adesignated speed zone.

As yet another example, an event may trigger the recognition of ageo-feature 402 such as a speed zone only where an industrial vehicle108 enters the speed zone, and it is a certain time of the day, e.g.,first shift, enters from a specific direction, etc.

Properties 404 may also define a desired action. Numerous exampleactions include a process to start or set a window around recordedevents to encapsulate a record of the industrial vehicle encounter withthe geo-feature 402. Here, the data logging capability of the processingdevice 102 on the industrial vehicle 108 can begin to aggregateindustrial vehicle measurable or otherwise recordable information into ageo-feature encounter window. For example, speed, travel direction, forkheight, weight on forks, operator ID, time of day, task being performed,message(s) received from the geo-feature, response/reaction thereto, andother relevant data can be data logged in a geo-feature record. Thisrecord can thus provide a complete account of the encounter with thegeo-feature for subsequent auditing.

The properties 404 can also specify messaging or alerts to theindustrial vehicle operator, nearby pedestrians, or both.

Yet further, properties 404 can define automation to control theindustrial vehicle 108, e.g., to set limits of operation, to causespecific industrial vehicle controls to operate in a predeterminedsequence, etc.

Still further, where the geo-feature 402 is a prompt zone, there may bemultiple messages associated with the prompt zone, e.g., to providecritical messages, alerts, warnings, pre-action instructions, postaction affirmations or negative reinforcements, etc., based upondetected conditions.

Moreover, each prompt may be tied to a different output device, e.g.,via display of text, output of voice command, use of lights, sounds,haptic response, etc. For instance, a prompt zone may be configured todisplay the message “Stop Ahead” on a display screen so long as theindustrial vehicle is traveling less than a predetermined speed.However, the message may be “Slow Down, Stop Ahead” on the displayscreen where the industrial vehicle speed exceeds a predeterminedthreshold. Alternatively, instead of using the display screen, thesystem may decide to sound an audible alarm, e.g., an audible tone orflash a colored light, to serve as an indication to the industrialvehicle operator that the industrial vehicle is traveling at an excessrate of speed.

Action zones may also be configured with messages. For instance, when anindustrial vehicle 108 exits a stop zone, if the industrial vehicle 108properly stopped, a message may provide a positive affirmation “StoppedCorrectly”. On the other hand, if the industrial vehicle operator failedto stop properly, a negative message may be conveyed “Failed to Stop”.Here, a process evaluates vehicle operating conditions and activity todetermine the appropriate time after the encounter with the geo-feature402 to provide the necessary information.

Numerous other applications can be readily contemplated and are thuswithin the spirit of the disclosure herein. Basically, if a property 404can be defined by a static value, variable, rule, formula, algorithm,state machine, measure, or other determinable manner, the property canbe applied to the geo-feature as geo-feature information.

Once one or more geo-features 402 are defined, the graphical userinterface 304 uploads the geo-features 402. The upload may be to aserver (e.g., server 112 in FIG. 1), or ultimately to the industrialvehicles 108 themselves. In an example implementation, the industrialvehicles 108 of FIG. 1 are equipped with environmental based locationtracking features (see for instance 220 of FIG. 2). This allows theindustrial vehicle 108 to be aware of its position, orientation, traveldirection, etc., within the environment of the warehouse. In this regardthe geo-features 402 (or a subset thereof) may be uploaded into theindustrial vehicle 108 such that operation of the industrial vehicle 108within the corresponding physical environment triggers the event andcorresponding action when the industrial vehicle 108 encounters aphysical location associated with the geo-feature 402. Thus, in thisexample implementation, the industrial vehicles themselves detectgeo-features 402, and process all the execution requirements of thegeo-feature 402 based upon geo-feature information, position information(as determined by the environmental based location tracking 220, andbased upon operational (state) information regarding the currentoperating state of the industrial vehicle 108. The current operatingstate can include the state of encoders, switches, controllers, speed,direction, heading, weight on the forks, battery charge, etc.

Referring to FIG. 4B, there may be occasion where there are numerousgeo-features. As such, the graphical user interface 304 allows the userto configure geo-features 402 in layers, e.g., using a layer menu 420.For instance, there may be geo-features that are to be utilized by allvehicles, which may be in a layer. A separate layer can be used to setup geo-features for a certain truck, type of truck, operator, type ofoperator, shift, team, or any other desired delineation. This allows theability to reduce clutter on the screen. Moreover, multiple layers canbe combined to overlay geo-features.

Also, setting up geo-features 402 by layers enables the user to includeor not include specific properties (e.g., unique measures) for a selectinstance or group of instances that a geo-feature 402 is intended. Forexample, a geo-feature 402 such as a speed zone can have a first speedlimit for first shift operators, but a second speed limit for secondshift operators.

As another example, a geo-zone such as a speed zone may impose a speedrestriction on all vehicles, but also require a specific operator (suchas an operator-in-training) to travel in a certain direction, travelwith forks lowered, not perform blending in the area etc. This abilityis easily handled with layers.

Geo-features can also be set up based upon tasks to be performed, suchas by integrating with a WMS system (e.g., analogous to that describedabove). Here, a layer provides a convenient way to organize geo-featuresthat are task-based. Examples of task-based geo-features are describedmore fully herein.

Vehicle-Based Events:

The system can also be used to track and respond to events that are notlocation based per se. Here, vehicle based events can be detected and aresponse can be triggered and carried out in response to the detectedevent.

Referring to FIG. 4C, the graphical user interface is used to set upevent descriptions to capture events that are vehicle-based. However,instead of drawing a zone or identifying a feature on the model of thewarehouse, the user enters information such as properties that definethe event, and the desired response to the event. In the examplegraphical user interface 304, the user selects a truck based events dropdown 430 to enter vehicle-based geo-features and properties. In thisregard, the process, responses such as messaging, event recording, etc.,is analogous to that of FIGS. 4A and 4B. For instance, in operation,when the event is detected, the corresponding event description cantrigger geo-information to be assembled with vehicle data into an eventrecord to capture the vehicle state and location/movement surrounding anevent of interest. The event description can also include instructionsto carry out a desired response, such as provide a message, feedback,take an action, etc.

A non-exhaustive list of events of interest include detecting that achecklist was completed in less time than a predetermined minimum timeto complete the checklist or detecting that a checklist was completed inmore time than a predetermined maximum time to complete the checklist.

Additional examples of events include detecting an impact associatedwith the industrial vehicle; detecting at least one of erratic steeringwith raised forks, fast steering with raised forks, cornering high speedwith raised forks, braking suddenly with an elevated load, etc. Yet moreexamples include detecting at least one of exceeding a predeterminedheight extended travel while in free lift, the forks are extended andthat the industrial vehicle is traveling with the forks elevated, that areach is extended and that the industrial vehicle is traveling with thereach extended, etc. Still further, vehicle based events can includedetecting at least one of an event where the industrial vehicle isoperating with an undersized battery, the industrial vehicle isoperating with an underweight battery, early or late battery charges,improper battery care, including water schedule and proper cycling, atrigger associated with a battery equalization schedule, utilization ofan efficiency driving style profile, utilization of an excess of energyusage based upon a detected driving profile, the usage of a specifictype of fuel usage, fuel/battery run-out events, etc.

Other example vehicle related events include by way of example,detecting excessive travel of the industrial vehicle outside typicaldistance, detecting that lift usage cycles of the industrial vehicle areoutside a range of typical cycles, etc. Events can also comprisedetecting the presence of an idle operator on a stationary industrialvehicle where the operator is logged into the industrial vehicle or anoperator is logged into an industrial vehicle but is not present on theindustrial vehicle; detecting that an operator exited the industrialvehicle while the industrial vehicle is still moving; detecting that aload capacity is over a predetermined capacity load limit; and detectingthat the industrial vehicle is traveling on a ramp in an improperdirection.

As with the examples of FIGS. 4A, 4B, the properties also include aresponse to the detection of the event, e.g., generation of a message,encapsulation of event data into an event record that is sent to theserver 112, etc. Moreover, location information, e.g., from theenvironmental based location tracking 220 of FIG. 2 can be used tointegrate location information into the event record to capture vehicleactivity before, during and after the event, as set out in greaterdetail herein. Such information is also sent back to the server 112.

Referring to FIG. 4D the graphical user interface 304 can also includeone or more menus 440 to provide reports of collected event data. Onesuch example report allows a user to navigate the model 306 (and layerswhere used) to identify geo-features 402 that triggered the generationof event records. The user can then select events, and review theproperties associated therewith. This includes for instance, playingback simulations (as described in greater detail with reference to FIGS.6D-6G), identifying operator data, vehicle identification data, andvehicle state data, along with other collected data in the event record.The reports can include filters, e.g., by layer, truck, truck type, daterange, etc.

Referring to FIG. 4E, the graphical user interface 304 can also includea menu 450 that allows prioritization and conflict resolution wheremultiple geo-features 402 and/or events overlap or otherwise causeconflict. This optional feature allows the customization andprioritization of event responses. For instance, a geo-feature 402 thatis higher in a hierarchy can trump, over-ride, negate, void, reinforceor otherwise modify a behavior relative to a geo-feature lower in thehierarchy.

Example Approach to Geo-Feature Deployment:

Referring to FIG. 5, a process and hardware computing device to generatea graphical user interface for interacting with industrial vehicles isprovided. The approach 500 can be executed by a processor coupled tomemory, where the processor executes program code stored in the memoryto carry out the approach, e.g., via a processing device 102 describedmore fully herein.

The approach 500 comprises presenting at 502, on the graphical userinterface, a model depicting a graphical representation of a virtualenvironment that corresponds to a physical environment, where thephysical environment is contained within a bounded region. For instance,the physical environment can be contained within a bounded region suchas a mapped portion of a warehouse. The approach 500 also includesproviding, at 504, a tool with the graphical user interface that enablesa user to define a geo-feature at a location on the model. Here, thegeo-feature corresponds to an element within the virtual environmentthat transforms into an industrial vehicle control in the correspondingphysical environment such that an event triggers a corresponding actionon an industrial vehicle within the corresponding physical environmentwhen the industrial vehicle encounters the geo-feature. The approach 500still further comprises opening, at 506, a dialog box within thegraphical user interface that enables the user to enter a parameter thatdefines at least one of a function, characteristic, or action of thedefined geo-feature. Further, the approach 500 comprises uploading, at508, the defined geo-feature such that operation of the industrialvehicle within the corresponding physical environment triggers the eventand corresponding action when the industrial vehicle encounters aphysical location associated with the geo-feature.

As noted more fully herein, the tool provided with the graphical userinterface can enable a user to define a geo-feature on the model byproviding a tool that enables the user to draw a geo-zone on the model,where a geo-zone is an area on the model that corresponds to a desiredgeo-feature. Here, the user can draw any number of geo-features aszones, including for example, an action zone that defines a zone wherethe industrial vehicle is expected to perform a predetermined action anda prompt zone that defines a zone where the industrial vehicle is toprovide a message, e.g., alert, information, or other action to bringabout situational awareness.

For instance, an action zone may comprise a restriction zone thatdefines a zone that the industrial vehicle is to stay out of, an idlezone that defines a zone where the industrial vehicle is to remain forless than a predetermined amount of time, a speed zone that defines azone where the industrial vehicle is to maintain a predetermined maximumspeed, a control zone that defines a zone where an automation featuretakes control of the industrial vehicle, a height restrict zone thatdefines a zone where the industrial vehicle is to maintain forks and/orthe mast below a predetermined maximum height, a stop zone that definesa zone where the industrial vehicle is to stop, a horn zone that definesa zone where the industrial vehicle is to sound a horn, etc.

Referring back to FIG. 4, geo-features can be aggregated to bring outcomplex actions. For instance, a geo-feature 402 such as a prompt zonecan be placed adjacent to an action zone to provide a message indicatingthe desired industrial vehicle action when the industrial vehicleencounters the adjacent action zone. As such, a warning can be providedvia the prompt zone that an end of aisle stop is required. A geo-featuresuch as a stop zone can be placed at the end of the aisle to capturewhether industrial vehicles properly stop. As another example, ageo-feature such as a horn zone can be placed on top of (or underneath)a geo-feature such as a stop zone to require two discrete actions, stopthe industrial vehicle and sound the horn.

As another example, a prompt zone can overlap with an action zone sothat the prompt from the prompt zone remains active during the encounterwith the corresponding action zone.

Still further, the graphical user interface can open a dialog box thatenables the user to enter a parameter that builds a condition for thegeo-feature that is contingent upon a state of a process running in adomain associated with a task being performed by an operator of theindustrial vehicle, build a condition for the geo-feature that iscontingent upon a state operation of the industrial vehicle, build acondition based upon the state of other meta data, e.g., operator ID,time of day, shift, team, vehicle type, etc.

Vehicle Monitoring with Event Replay:

Referring to FIG. 6A, assume that an industrial vehicle 108 equipped todetect geo-features is traveling down an aisle 602 in the direction ofthe arrow directly above the industrial vehicle 108 (e.g., travelingleft to right as illustrated). In this example, the industrial vehicleis about to encounter two geo-features, including a prompt zone 604 anda stop zone 606.

Referring to FIG. 6B, when the industrial vehicle encounters the promptzone 604, the industrial vehicle processes the prompt zone information.In this example, the industrial vehicle 108 conveys a prompt to thevehicle operator “STOP AHEAD”. Because of the overlap of the prompt zone604 and the stop zone 606, the prompt will persist until the industrialvehicle exits the stop zone. Color can be used in the display toindicate the message as being informational. The occurrence of thisevent is documented in one or more event records that are communicatedback to the server 112.

If the industrial vehicle 108 would have come to a complete stop at thestop zone, then either a positive reinforcement message may bedisplayed, or no message is displayed. However, assume for this examplethat the operator did not stop.

Referring to FIG. 6C, assume the operator drove through the stop zonewithout bringing the industrial vehicle to a full stop. In responsethereto, assume that the geo-feature information for the stop zoneincludes properties that trigger the industrial vehicle to issue afirst, immediate response, e.g., an audible tone, flashing light,illuminated colored light, etc., indicating that the vehicle operatorfailed to stop. A separate conditional algorithm is also triggered thatwaits until predetermined conditions are met, e.g., the industrialvehicle is removed from the stop zone (e.g., 15-20 feet away), and thenwhen the conditions are satisfied, triggers a second message, e.g., aprompt of text on a display screen that reads “FAILED TO STOP”, or someother suitable message. This occurrence is documented in one or moreevent records that are communicated back to the server 112.

As noted in greater detail herein, in an example implementation, theencounter with the geo-features 604, 606 triggers a recording window(e.g., before, during, and after the encounter with the geo-features).This recording window captures event data associated with the encounter,and that data is sent to a remote server, e.g., server 112 in FIG. 1. Byway of example, the system can capture event data, e.g., industrialvehicle truck data (e.g., speed, travel direction, fork height, forkload, etc.) operational data (e.g., time of day, shift, operator ID,etc.) information about the geo-features, etc., as an industrial vehicleencounters one or more geo-features. In an illustrative example, thesystem captures over 10 seconds of data before encountering ageo-feature, and continues to data log until over 10 sections after theengagement with the geo-feature ceases. In this regard, the system cancapture the properties associated with the geo-features, and how theindustrial vehicle reacts thereto. Other time windows can be used tocapture data before, during, and after the encounter with a geo-feature,e.g., using a rolling window recorder, circular buffer, etc.

Once the server received the record, the server determines that animproper behavior was noted. As such, the server can send a message to amanager, supervisor, etc. via instant messaging, email or other form toraise an awareness of the infraction.

The manager, supervisor, etc., can then replay a simulation of the eventbased upon the record sent to the server.

Replay:

The model displayed by the graphical user interface can be used todisplay an “event density map” (e.g., FIG. 4D) of areas of the warehousewhere improper actions were taken in response to geo-features, events,or combinations thereof. As such, a user can select an area, select anevent, etc. and replay the associated event record to see the details ofthe event.

By way of example, referring to FIGS. 6D-6G, the graphical userinterface uses the created model to play back simulations of actualindustrial vehicle movement and industrial vehicle interaction withgeo-features (e.g., based upon data collected by the server 112).

By way of illustration and not by way of limitation, assume that anoperator improperly turned at an end of aisle without properly stopping,as described with reference to FIGS. 6A-6C. A manager, supervisor, etc.,can replay the event to see exactly what happened and what theconditions were surrounding the event. As illustrated at 6D, as theindustrial vehicle 108 approaches the first geo-feature 402 (a promptzone representing the geo-feature 602 in the physical environment),appropriate properties 610 (event data at a slice of time) of the eventcan be displayed (e.g., speed, travel direction, fork height, etc.).

With reference to FIG. 6E, the industrial vehicle 108 encounters thefirst geo-feature 402 (e.g., a prompt zone). Digging into the properties612, it can be seen that prompt message “STOP AHEAD” was provided to theoperator. This may be carried out by an audible message, voice message,text message on a display screen, light from a light bar or displayscreen, haptic response, etc., as noted in greater detail herein. Theevent parameters represent the recorded event data later in timecompared to the properties 610 of FIG. 6D. Thus, one can determinewhether the operator attempted to slow down in response to the prompt bycomparing the vehicle speed in the properties 610 of FIG. 6D to thevehicle speed in the properties of FIG. 6E.

In FIG. 6F, the industrial vehicle 108 exits the first geo-feature 402,and now enters a second geo-feature, i.e., stop zone. Again, properties614 related to the recorded event are shown. At the stop zone, theindustrial vehicle is supposed to stop. As such, the system has loggeddata evidencing whether the operator properly stopped.

In FIG. 6G, the replay of the action of the industrial vehicle 108continues through the geo-feature of interest. Again, properties 616 ofthe event can be displayed. Here, the properties show that theindustrial vehicle failed to stop and that a negative reinforcementmessage was displayed, e.g., a message “FAILED TO STOP” was presented tothe vehicle operator.

Failure to demonstrate appropriate actions in response to geo-featurescan in some embodiments, result in punitive results, e.g., theperformance abilities of the industrial vehicle can be temporarilydetuned until appropriate actions are demonstrated by the vehicleoperator in response to the geo-feature.

Although provided in the context of a stop zone for convenience ofillustration, the above can be applied to any other geo-feature types,with appropriate actions predicated by the type of geo-feature.

Thus, the system receives event data indicative of a select industrialvehicle encountering a geo-feature, provides on the graphical userinterface, the model, depicts a vehicle icon as a graphicalrepresentation of the select industrial vehicle superimposed on themodel, and animates the industrial vehicle icon so as to replay theevent associated with the industrial vehicle encountering thegeo-feature based upon event data collected from a real, physicalencounter of the corresponding industrial vehicle with the geo-feature.

Moreover, the graphical user interface can provide a dialog box thatpresents industrial vehicle operational data recorded during theencounter with the geo-feature (e.g., based upon informationcommunicated from the industrial vehicle 108 back to the server 112).Still further, as noted, the graphical user interface provides theanimation so as to replay events recorded both before and after theselect industrial vehicle actually encountered the geo-feature. Also,the graphical user interface can be used for aggregating a plurality ofindustrial vehicle encounters with a select geo-feature so as to displayon the graphical user interface, an aggregation of data with regard tomultiple industrial vehicle encounters with geo-features. Analogously,icons of vehicles can be selected to display vehicle metadata, recordedevent data, operator data, timestamps, etc.

Since each encounter with a geo-feature is saved as an event record atthe server, the geo-feature encounters across a fleet of vehicles can beanalyzed for various purposes.

Also, in some implementations, e.g., where the industrial vehicle isequipped with a robust display, the operator may be able to use thereplay feature to replay an account of an encounter with a geo-feature.

Real-Time Monitor:

Additionally, where the server 112 of FIG. 1, collects positioninformation from the industrial vehicles, a real-time monitor can begenerated. Here, an icon representing each instance of an industrialvehicle is depicted on the model. As such, a supervisor, manager,analyst, etc., can watch the industrial vehicles as they move about thewarehouse. Moreover, since the model is tied to the creation ofgeo-features, the geo-features can also be displayed, and the parametersassociated the geo-feature encounters can be displayed, in a manneranalogous to those approaches set out herein.

Industrial Vehicle Interactions with Geo-Features in the Warehouse:

Referring now to FIG. 7A, a process 700 is shown. The process 700 may beused, for instance, for conveying a message on an industrial vehicle.The process 700 can be implemented on any of the processing device 102of FIG. 1. Moreover, the process 700 may be implemented by the purposebuilt computer illustrated in FIG. 2, e.g., a processor on an industrialvehicle 108.

At 702, the industrial vehicle receives geo-feature information about apredefined geo-feature. For instance, geo-feature information about apredefined geo-feature can include information about at least one of apredefined fixed geo-feature, a predefined mobile geo-featuresurrounding the industrial vehicle, and a predefined mobile geo-featureidentified as a geo-feature around another industrial vehicle.

The process 700 can also permit the processor on the industrial vehicleto dynamically generate a geo-feature, e.g., in response to a detectedimpact involving the industrial vehicle.

In an example, the geo-feature is located in an area upon which theindustrial vehicle may travel, e.g., by identifying the geo-feature in amapped portion of a warehouse. In an example configuration, a wirelesstransceiver (e.g., 202 of FIG. 2) is coupled to the industrial vehicle108, and geo-feature information entered by a user at a terminal (e.g.,server, workstation, mobile device, tablet etc. in any of the processesdescribed herein) is transmitted to the industrial vehicle via thewireless transceiver (optionally through server 112 of FIG. 1).

The geo-feature information can include the geo-feature's location(e.g., absolute location within a facility, a central point and aradius, borders drawn by the user, etc.) and shape. Further, thegeo-feature information can include properties as set out in greaterdetail herein, such as rules to determine when the geo-feature is to beencountered, a geo-feature including an expected operating state of avehicle in the geo-feature. For example, a geo-feature may be apredefined zone, such as a prompt zone, an action zone, or both. Aprompt zone is a zone where a message is conveyed upon entering theprompt zone and is usually paired with an action zone. On the otherhand, an action zone is a zone where the industrial vehicle takes anaction (e.g., recording an operating state and location of theindustrial vehicle), responds to an action by an operator of theindustrial vehicle (e.g., determines if the operator stopped properly,checks the speed of the industrial vehicle, etc.), or both. Examples ofaction zones include, but are not limited to: reduced-speed zones,control zones, restricted-height zones, restricted access zones, idlezones, stop zones, sound-horn zones, etc. Each action zone may have oneor more message zones adjacent, overlapping, or collocated with theaction zone. For example, as an operator approaches a stop zone, theoperator may travel through a message zone that informs the operator tostop in the next zone.

Further, a geo-feature may be a mobile zone. For example, a mobile zonemay be moved throughout the facility (e.g., the mobile zone may be azone surrounding an industrial vehicle, a pallet, etc.).

Still further, a geo-feature may be transient in nature. For example, ageo-feature can be tied to the detection of an occurrence of an impactinvolving the industrial vehicle. If an impact is detected, ageo-feature is created around the impact event, and processing iscarried out as described in greater detail herein. By way of example, ifa significant number of impacts happen at the same location, it may bethat there are no actual impacts. Rather, impact sensors on industrialvehicles may be triggering due to a facility problem, e.g., crack in thefloor, etc. As such, a geo-feature can be set up to ignore reports ofimpacts at the specific location of the known facility problem until theproblem is corrected. Here, it may be desirable to require that amanager manually create the geo-feature, and then take the geo-featuredown once the facility problem is remedied. In certain implementations,the system can be intelligent, so as to expunge previously reported andrecorded impacts where it is judged that the impact was a facility issueat the designated location of the geo-feature, and not a true impact. Assuch, an operator is not improperly penalized for improper vehicleoperation.

At 704, the industrial vehicle monitors (e.g., continuously) locationinformation identifying a current location of the industrial vehicle.Here, the term “continuously” means repeatedly, such as in a continuousor recurring cycle, and thus includes periodic discrete measurements,accounting for practical delays in processing circuitry. For instance,vehicle position may be updated electronically several times a second.On the other hand, slower moving industrial vehicles may update everysecond or longer, depending upon the desired resolution to adequatelytrack the vehicle position.

As noted in greater detail herein, the industrial vehicle may include asystem that tracks its location based on landmarks within the facility,e.g., using the environmental based location tracking 220 of FIG. 2. Asanother example, the industrial vehicle may include a global positioningsystem (GPS), triangulation system or other system that allows locationto be determined. As a further example, the industrial vehicle mayinclude a transponder, and the position of the industrial vehicle may betriangulated within the facility. Other methods may be used to determinethe industrial vehicle's location.

Regardless of the method used to determine the industrial vehicle'slocation, the industrial vehicle collects the location information. Forexample, if the location information is determined on the industrialvehicle itself, then the industrial vehicle already has access to thelocation information. However, if the location information is determinedoff of the industrial vehicle, then the location information istransmitted to the industrial vehicle (e.g., via the wirelesstransceiver). Here, the location information reflects the currentlocation of the industrial vehicle as the industrial vehicle is operated

At 706, the industrial vehicle collects operation information about acurrent operating state of the industrial vehicle. For example, theoperation information may be collected from subsystems of the industrialvehicle (e.g., traction system, hydraulic system, accelerometers,controller states, switch states, etc.) and stored in memory on theindustrial vehicle, e.g., by collecting information fromcontrollers/modules 216 across a industrial vehicle network system 214for storage and processing by the control module 204 of FIG. 2.

Upon detecting that the industrial vehicle encounters the geo-feature,the process further comprises generating at 708, an output message basedon the geo-feature information, the location information, and theoperating information. In an example implementation, the output messageis generated by determining an expected operating state of theindustrial vehicle from the geo-feature information, where the expectedoperating state includes an acceptable range, and comparing the currentoperating state of the industrial vehicle to the expected operatingstate. For instance, the process may identify an acceptable range forthe expected operating state selected from the group consisting of speedof the industrial vehicle, a height of forks of the industrial vehicle,a time that the industrial vehicle may remain in the predefinedgeo-feature, and an orientation of the industrial vehicle. The processthen generates at least one of a first message as the output messagewhere the comparison indicates that the current operating state iswithin the acceptable range of the expected operating state, and asecond message as the output message, different than the first message,where the current operating state is outside the acceptable range of theexpected operating state.

The process 700 can further comprise determining whether the predefinedgeo-feature is a message zone or an action zone, determining whether theindustrial vehicle has encountered the predefined geo-feature, andstoring, periodically, the operational information and the locationinformation at least during the encounter with the geo-feature, as notedmore fully herein. Here, conveying the output message further includesconveying the message on the industrial vehicle where the industrialvehicle is within the message zone. For example, if the industrialvehicle is traveling down an aisle and encounters a geo-feature (thusgenerating location information), where the geo-feature is implementedas a message zone (thus generating zone information) with forks of theindustrial vehicle raised (thus generating operation information), thena certain message may be generated. However, if the operator enters thesame zone with the forks lowered, a different message may be generated.An exemplary embodiment of 708 is described below in reference to712-718 in regard to FIG. 7B, described below.

At 710, the output message is conveyed on the industrial vehicle. In anexample configuration, the process 700 can further comprise selecting anoutput device for conveying the message based on at least one of: theoperating information, a speed of the industrial vehicle, and anorientation of the industrial vehicle. Moreover, the process 700 canfurther comprise configuring at least two types of output messagesincluding a first type of message as text on a screen of the industrialvehicle, and a second type of message on a screen of the industrialvehicle without using text. In this configuration, conveying the outputmessage further comprises selecting whether to display the first type ofmessage or the second type of message and displaying the selected typeof message. Yet further, where the industrial vehicle comprises a firstlight visible to an interior of the industrial vehicle and a secondlight visible to an exterior of the industrial vehicle, the process 700can comprise activating at least one of the first light and the secondlight of the industrial vehicle upon outputting the message.

For example, the output message may be displayed as text on a displayscreen attached to the industrial vehicle, as a symbol on the displayscreen, presented as an illuminated light mounted to the industrialvehicle that may be seen from an interior of the industrial vehicle, asa light mounted to the industrial vehicle that may be seen from anexterior of the industrial vehicle (e.g., by pedestrians), orcombinations thereof.

Pedestrian communication is not limited to lights. Rather, lights, radiofrequency, optical, RFID, ultrasonic communication (which is receivedand converted to a pedestrian feedback), and other technologies can beutilized to communicate intended information.

In yet another example implementation, the processor on the industrialvehicle identifies a current location of an industrial vehicle andcollect operation information about a current operating state of theindustrial vehicle by collecting the operational information. Inresponse to detecting a geo-feature, the processor then causes thesystem to display a message on a display on the industrial vehicle.

Referring now to FIG. 7B, an optional process is disclosed for carryingout the generation of the output message at 708 of FIG. 7A.

At 712, an expected operating state of the industrial vehicle isdetermined based on a geo-feature (e.g., zone information) and operationinformation. For example, if the industrial vehicle enters a geo-featuresuch as a combined action/message zone that is a restricted-speed zone,then an expected operating state may be that the industrial vehicle istraveling between one and three miles-per-hour. As another example, ifthe industrial vehicle enters a restricted-height zone, then theexpected operating state may be that the forks are below a maximumdesignated height. This may be required for example, to ensure that theindustrial vehicle can pass under a lower ceiling, through a doorway,etc. As a further example, if the industrial vehicle enters ahigh-traffic zone, a speed zone may be generated such that the expectedoperating state (speed) of the industrial vehicle is between two andfive miles-per-hour. As another example, an idle zone may include anexpected operating state that the industrial vehicle may not remain inthe idle zone for more than five minutes. As indicated in the examplesabove, the expected operating state may include a range of acceptablevalues.

At 714, the expected operating state is compared to the currentoperating state (i.e., the operation information) to determine whetherthe current operating state is within the acceptable range of theexpected operating state. If the current operating state is within theacceptable range of the expected operating state, then at 716, a firstmessage is determined as the output message. However, if the currentoperating state is outside the acceptable range of the expectedoperating state, then at 718, a second message (different from the firstmessage) is determined as the output message.

For example, if the industrial vehicle enters a geo-feature such as amessage zone adjacent to a geo-feature implemented as a stop zone, thenan expected speed range is determined (e.g., less than twomiles-per-hour). If the current speed of the industrial vehicle is fourmiles-per-hour, then message may be SLOW DOWN, STOP AHEAD. However, ifthe current speed of the industrial vehicle is one mile-per-hour, thenmessage may be STOP AHEAD.

Conditions:

Moreover, the process in which the message is displayed may be dependenton the current operating state of the industrial vehicle. For example,if the message is STOP AHEAD and if the industrial vehicle is travelingbelow two miles-per-hour, then a display may read STOP AHEAD. However,if the industrial vehicle is traveling between two and threemiles-per-hour, then the message may be converted to a flashing light,text free display on the display screen (e.g., a red octagon, etc.).Alternatively, if the industrial vehicle is traveling over threemiles-per-hour, then the message may be SLOW DOWN, STOP AHEAD, but thatmessage may be converted to activate a red light on the interior of theindustrial vehicle, so the operator does not need to look away from theaisle to determine the message. By changing the messages and the waythose messages are displayed, the operator is less likely to suffer from“warning overload” where the operator sees so many warnings and alertsthat most of them are ignored. Moreover, by avoiding detailed text basedmessages when the industrial vehicle operator is engaged in operatingthe industrial vehicle, distraction may be reduced.

FIG. 8 illustrates an example of the use of conditions with the process700 of FIG. 7A (and optionally 7B). A user sets up a fixed restrictedzone 802 at an edge 804 of an aisle 806 of a facility, e.g., asdescribed above, e.g., with regard to FIGS. 3-5. The restricted zone 802acts as a buffer between the aisle 806 and a zone 808 where pedestriansmay walk and where pallets 810 are kept. However, there may besituations where the industrial vehicle may have to breach the zone 808,such as to pick up an intended load. As such, properties can include“exclude” or “exception” conditions. For instance, an expected operatingstate of the industrial vehicle in the restricted zone 802 may be thatthe industrial vehicle is traveling below a predetermined speed, e.g.,one mile-per-hour, and enters at an orientation angle suggestive ofpicking up a pallet, e.g., eighty-five to ninety-five degrees. As such,these parameters are encoded as exception properties. Then, zoneinformation regarding the restricted zone 802 is wirelessly transmittedto an industrial vehicle 812. Thus, the industrial vehicle 108 collectszone information about the predefined zone (i.e., 802 of FIG. 8). As anoperator of the industrial vehicle 108 performs tasks with theindustrial vehicle 108 around the facility, location information andoperation information is collected (i.e., 704 and 706 of FIG. 7).

In this example, the industrial vehicle 108 is assigned to move thepallet 810 to a different location. Therefore, the operator follows apath 812 that allows the industrial vehicle 108 to pick the pallet 810.When the industrial vehicle 108 encounters the geo-feature (e.g., entersthe restricted zone 802), the expected operating state is determined(i.e., 710 in FIG. 7) and compared to the current operating state (i.e.,712 of FIG. 7). In this case, assume the industrial vehicle 108 hasentered the restricted zone 802 at a ninety degree angle at a speed ofone-half miles-per-hour. Recall that the expected operating state of theindustrial vehicle in the restricted zone 802 is that the industrialvehicle is traveling below one mile-per-hour and enters at anorientation angle of eighty-five to ninety-five degrees. Therefore, theresult of the comparison indicates that the current operating state iswithin the acceptable range of both conditions of the expected operatingstate. As such, a message (i.e., 714 of FIG. 7) indicating that therewas an acceptable entry into the restricted zone is displayed (i.e., 718of FIG. 7). Alternatively, no message may be conveyed at all when thereis a successful entry (i.e., the message determined at 714 of FIG. 7 is“no message”).

Turning now to FIG. 9, later in the day, the industrial vehicle 108starts to drift into the restricted zone 802. When the industrialvehicle 108 enters the restricted zone 802, the expected operating stateis determined (i.e., 710 in FIG. 7) and compared to the currentoperating state (i.e., 712 of FIG. 7). In this case, the industrialvehicle 108 has entered the restricted zone 802 at a thirty degree angleat a speed of one-half miles-per-hour. Therefore, the result of thecomparison indicates that the current operating state is outside theacceptable range of the expected operating state. As such, a message(i.e., 714 of FIG. 7) indicating that there was an unacceptable entryinto the restricted zone is conveyed (i.e., 718 of FIG. 7), e.g., via atextual message on the display of the industrial vehicle, a light, asound, an audible voice command/message, a haptic response, etc.

Assume the industrial vehicle 108 enters a geo-feature 802 at a thirtydegree angle at a speed of five miles-per-hour, then the messageindicating an unacceptable entry may be converted to a flashing redlight in the interior of the industrial vehicle 108. Moreover, a lighton the exterior of the industrial vehicle 108 may illuminate, e.g.,flash to warn pedestrians of the breach, an alarm sound may be sounded,etc.

Regardless, the industrial vehicle logs the location information andoperation information a preset duration before the geo-feature, whilethe industrial vehicle 108 remains in the geo-feature, and for a presetduration after the industrial vehicle exits the geo-feature.

FIG. 10 shows another example of the process 700 of FIG. 7A. In thisexample, a user sets up a first stop zone 1002 and a second stop zone1004 in an aisle 1006 on opposite sides of a pedestrian walkway 1008. Athird zone 1010 is placed before the first stop zone 1002 and is amessage zone that warns the operator that a stop zone 1002 is ahead. Afourth zone 1012 is placed before the second stop zone 1004 and is amessage zone analogous to the third zone 1010, but the message warns theoperator of stop zone 1004 ahead. The above is set up, such as describedmore fully herein with regard to FIGS. 3-5. The zone information,location information, and operation information are collected (702, 704,and 706 in FIG. 7) as above. When an industrial vehicle 108 enters leftto right in the FIGURE, the industrial vehicle encounters the firstgeo-feature (i.e., the message zone 1010) that informs the operator ofthe industrial vehicle of the stop zone 1002 ahead. The industrialvehicle enters the stop zone 1002 and is expected to stop at the end ofthe aisle adjacent to zone 1002. When the industrial vehicle 108 drivesthrough the walkway 1008, it encounters another geo-feature (the stopzone 1004). However, this time, the geo-feature 1004 detects that theindustrial vehicle is traveling left to right in this example, and assuch, this geo-feature does not apply to the industrial vehicle 108. Assuch, the geo-feature 1004 does not provide a message to the vehicleoperator to stop. Moreover, the geo-feature 1012 does not provide amessage to the vehicle operator informing of the impending stop becausethe industrial vehicle is traveling in the wrong direction for themessage of prompt zone 1012 to be applicable.

On the other hand, were the industrial vehicle to be traveling right toleft in this example, the geo-features 1012 and 1004 would be applicableto the industrial vehicle, whereas the geo-features 1002 and 1010 wouldnot be relevant to the industrial vehicle. As such, any messaging,prompting, warning, scoring or other features of geo-features 1002 and1010 would not be performed in this example. Since the geo-features 1002and 1010 are judged to be not relevant to the industrial vehicle 108 inthis example, then no infraction of the geo-feature is recorded.

Vehicle Based Event Detection:

Referring to FIG. 11, in an industrial vehicle, a machine-executableprocess 1100 is illustrated. The process 1100 can be implemented on anyof the processing device 102 of FIG. 1. Moreover, the process 1100 maybe implemented by the purpose built computer illustrated in FIG. 2,e.g., a processor on an industrial vehicle 108.

The process 1100 comprises identifying at 1102 (e.g., by a processor onthe industrial vehicle) an event that is related to an operation that isbeing carried out on the industrial vehicle, and collecting at 1104operation information about a current operating state of the industrialvehicle. The process 1100 also comprises performing at 1106 upondetecting that the event has occurred based upon the collectedoperational information, one or more actions. In an exampleconfiguration the actions comprise detecting the location of theindustrial vehicle at the time of the occurrence of the event,generating an event record encapsulating the collected operationalinformation from a time before the detected event until a time after thedetected event, the event record including at least one of capturedinformation indicative of direction, heading, and speed of travel of theindustrial vehicle, integrating information indicating the detectedlocation of the industrial vehicle into the event record, and wirelesslytransmitting the event record to a server computer.

Still further, the process 1100 comprises generating at 1108 an outputmessage based on the detected event, and conveying at 1110 the outputmessage on the industrial vehicle.

The process may also comprise detecting the location of the industrialvehicle at the time of the occurrence of the event, such as bycontinuously monitoring location information identifying a currentlocation of an industrial vehicle (e.g., using the environmental basedlocation tracking 220 of FIG. 2 and/or other techniques as describedmore fully herein). Here, the process can integrate the detectedlocation information into the event record by integrating locationinformation into the event record so as to capture the location of theindustrial vehicle before the detected event, during the detected event,and after the detected event.

By way of example, the process may generate an event recordencapsulating the collected operational information from a time beforethe detected event until a time after the detected event, integratingthe detected location information into the event record in a manneranalogous to that set out in greater detail herein. Also the process caninclude wirelessly transmitting the event record to a server computer.For instance, detecting the location of the industrial vehicle at thetime of the occurrence of the event can be carried out by continuouslymonitoring location information identifying a current location of anindustrial vehicle. Also, integrating the detected location informationinto the event record can include integrating location information intothe event record so as to capture the location of the industrial vehiclebefore the detected event, during the detected event, and after thedetected event. In addition to location information, the event recordcan also capture the direction, heading, speed of travel, etc., of theindustrial vehicle. Also, as noted more fully herein, vehicle state,operator data, timestamps, etc., can also be accumulated into the eventrecord.

As an example, if an aggressive steer is detected regardless oflocation, the system generates an event record that includes data from atime before the aggressive steer event, during the aggressive steerevent, and a time after the aggressive steer event, (along withlocation, direction, speed, and other data as described more fullyherein) and uploads this event record to the server 112. The system alsogenerates a message, e.g., “WATCH STEERING”, sounds an audible tone,provides a voice response, illuminates a light, or provides otherfeedback as noted more fully herein.

This simplified example is presented by way of illustration. Furtherexamples of identifying an event comprises identifying at least one of:detecting an impact associated with the industrial vehicle, detectingerratic steering with raised forks, detecting fast steering with raisedforks, detecting cornering high speed with raised forks, detectingbraking suddenly with an elevated load, detecting that a load capacityis over a predetermined capacity load limit, detecting exceeding apredetermined height extended travel while in free lift, detecting thatthe forks are extended and that the industrial vehicle is traveling withthe forks elevated, and detecting that a reach is extended and that theindustrial vehicle is traveling with the reach extended.

Further examples include identifying an event by identifying at leastone of: detecting that the industrial vehicle is operating with anundersized battery, detecting that the industrial vehicle is operatingwith an underweight battery, detecting early or late battery charges,detecting improper battery care, including water schedule and propercycling, detecting a battery equalization schedule, detecting anefficiency driving style profile, detecting an excess of energy usagebased upon a detected driving profile, detecting the usage of a specifictype of fuel usage, and detecting fuel/battery run-out events.

Yet further examples of identifying an event comprise identifying atleast one of: detecting excessive travel of the industrial vehicleoutside typical distance, detecting that lift usage cycles of theindustrial vehicle are outside a range of typical cycles, detecting thatthe industrial vehicle is traveling on a ramp in an improper direction,detecting the presence of an idle operator on a stationary industrialvehicle where the operator is logged into the industrial vehicle,detecting that an operator exited the industrial vehicle while theindustrial vehicle is still moving, and detecting an operator is loggedinto an industrial vehicle but is not present on the industrial vehicle.

Compliance Buffer:

In certain implementations, the thresholds can be “soft” or otherwiseinclude a buffer before treating an event or geo-feature encounter in anegative manner. A buffer can be established as a property in theassociated geo-feature or event.

For instance, if a geo-feature is a speed zone with a maximum limit of 5miles per hour, a programmed buffer may allow a variance of say ½ milean hour to account for environment conditions. By way of example, thespeed zone may be a long passageway, making it difficult to maintainprecise speed control over the distance of the speed zone.

When the vehicle enters the buffer condition upon encountering ageo-feature or event, a warning can be triggered, e.g., via a messageconveyed to the user in a manner as set out in greater detail herein.However, if the vehicle remains in the buffer region, or returns to anormal, expected condition for the speed zone, an event record need notbe generated. The concept of a buffer can be applied to numerous othergeo-features and events including those described more fully herein,thus the discussion above is not intended to be limiting.

Miscellaneous:

Aspects of the present disclosure request specific and timely vehiclebehavior e.g., in response to geo-features, events, etc. This requestedbehavior is often directly attributable to vehicle operator behavior.Regardless, the system monitors and documents compliance with theprogrammed and requested vehicle action. Again, this can also beattributed to operator action. The system also provides real-timefeedback to the vehicle whether compliance was attained or not.

In some implementations, some communication may occur during anincorrect behavior (e.g. speed zones, restricted areas, impacts, idletime, and height restrictions), when the operator can still correct thebehavior. On the other hand, some communication occurs after anincorrect behavior (e.g. stops and horn usage zones), letting theoperator know an incorrect behavior was performed.

The system may further provide the ability to enable a user to turn onand off certain properties of geo-features, e.g., to customize thegeo-feature experience.

Location Based Vs. Operation Based Variables:

As described more fully herein, the geo-feature properties includeprocessing capability to modify location based responses, e.g., enteringa prompt zone, and augmenting or altering a primary control (e.g.,present a text message on a display screen) with other control featuresbased upon operation based variables (e.g., vehicle speed, aggressivesteering, racing, etc.). For instance, the text message can be replaced,augmented, modified, etc., based upon detecting abnormal vehicleoperating characteristics.

Geo-Feature Visualization:

In some instances, it may be desirable to make the location ofgeo-features known to the vehicle operator. Geo-feature identificationcan be carried out through the use of lasers in the warehouse that mapout the boundary of geo-features. This use of lasers can be temporary ordisplayed for extended durations. Moreover, the display on theindustrial vehicle may be used to see the model of the warehouse withgeo-features identified thereon.

Computer System Overview

Referring to FIG. 12, a schematic block diagram illustrates an exemplarycomputer system 1200 for implementing the various process describedherein. The exemplary computer system 1200 includes one or more(hardware) microprocessors (μP) 1210 and corresponding (hardware) memory1220 (e.g., random access memory and/or read only memory) that areconnected to a system bus 1230. Information can be passed between thesystem bus 1230 and bus 1240 by a suitable bridge 1250. The bus 1240 isused to interface peripherals with the one or more microprocessors (μP)1210, such as storage 1260 (e.g., hard disk drives); removable mediastorage devices 1270 (e.g., flash drives, DVD-ROM drives, CD-ROM drives,floppy drives, etc.); I/O devices 1280 (e.g., mouse, keyboard, monitor,printer, scanner, etc.); and a network adapter 1290. The above list ofperipherals is presented by way of illustration, and is not intended tobe limiting. Other peripheral devices may be suitably integrated intothe computer system 1200. The memory 1220, storage 1260, removable mediainsertable into the removable media storage 1270 or combinationsthereof, can be used to implement the processes, configurations,interfaces and other aspects set out and described herein.

The microprocessor(s) 1210 control operation of the exemplary computersystem 1200. Moreover, one or more of the microprocessor(s) 1210 executecomputer readable code that instructs the microprocessor(s) 1210 toimplement the processes herein. The computer readable code may be storedfor instance, in the memory 1220, storage 1260, removable media storagedevice 1270 or other suitable tangible storage medium accessible by themicroprocessor(s) 1210. The memory 1220 can also function as a workingmemory, e.g., to store data, an operating system, etc.

The processes herein may be implemented as a machine-executable processexecuted on a computer system, e.g., one or more of the processingdevices 102 of FIG. 1, on a particular computing device such as thevehicle computer described with reference to FIG. 2, on a system 1200 ofFIG. 12, or combination thereof. In this regard, the processes hereinmay be implemented on a computer-readable storage device (e.g.,computer-readable storage hardware) that stores machine-executableprogram code, where the program code instructs a processor to implementthe described process. The processes herein may also be executed by aprocessor coupled to memory, where the processor is programmed byprogram code stored in the memory, to perform the described process.

Thus, the exemplary computer system 1200 or components thereof canimplement processes and computer-readable storage devices as set out ingreater detail herein. Other computer configurations may also implementthe processes and computer-readable storage devices as set out ingreater detail herein. Computer program code for carrying out operationsfor aspects of the present invention may be written in any combinationof one or more programming languages. The program code may executeentirely on the computer system 1200 or partly on the computer system1200. In the latter scenario, the remote computer may be connected tothe computer system 600 through any type of network connection, e.g.,using the network adapter 690 of the computer system 600.

In implementing computer aspects of the present disclosure, anycombination of computer-readable medium may be utilized. Thecomputer-readable medium may be a computer readable signal medium, acomputer-readable storage medium, or a combination thereof. Moreover, acomputer-readable storage medium may be implemented in practice as oneor more distinct mediums.

A computer-readable signal medium is a transitory propagating signal perse. A computer-readable signal medium may include computer readableprogram code embodied therein, for example, as a propagated data signalin baseband or as part of a carrier wave. More specifically, acomputer-readable signal medium does not encompass a computer-readablestorage medium.

A computer-readable storage medium is a tangible device/hardware thatcan retain and store a program (instructions) for use by or inconnection with an instruction execution system, apparatus, or device,e.g., a computer or other processing device set out more fully herein.Notably, a computer-readable storage medium does not encompass acomputer-readable signal medium. Thus, a computer readable storagemedium, as used herein, is not to be construed as being transitorysignals per se, such as radio waves or other freely propagatingelectromagnetic waves through a transmission media.

Specific examples (a non-exhaustive list) of the computer-readablestorage medium include the following: a hard disk, a random accessmemory (RAM), a read-only memory (ROM), an erasable programmableread-only memory (EPROM), Flash memory, a portable computer storagedevice, an optical storage device such as a compact disc read-onlymemory (CD-ROM) or digital video disk (DVD), or any suitable combinationof the foregoing. In particular, a computer-readable storage mediumincludes computer-readable hardware such as a computer-readable storagedevice, e.g., memory. Here, a computer-readable storage device andcomputer-readable hardware are physical, tangible implementations thatare non-transitory.

By non-transitory, it is meant that, unlike a transitory propagatingsignal per se, which will naturally cease to exist, the contents of thecomputer-readable storage device or computer-readable hardware thatdefine the claimed subject matter persists until acted upon by anexternal action. For instance, program code loaded into random accessmemory (RAM) is deemed non-transitory in that the content will persistuntil acted upon, e.g., by removing power, by overwriting, deleting,modifying, etc.

Moreover, since hardware comprises physical element(s) or component(s)of a corresponding computer system, hardware does not encompasssoftware, per se.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a,” “an,” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The description of the present disclosure has been presented forpurposes of illustration and description, but is not intended to beexhaustive or limited to the invention in the form disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the invention.

Having thus described the invention of the present application in detailand by reference to embodiments thereof, it will be apparent thatmodifications and variations are possible without departing from thescope of the invention defined in the appended claims.

What is claimed is:
 1. A machine-executable process in an industrialvehicle environment, comprising: electronically receiving by a processoron an industrial vehicle, geo-feature information about a geo-featurethat is located in an area upon which the industrial vehicle travels;detecting that the industrial vehicle has encountered the geo-feature;and performing, upon detecting that the industrial vehicle hasencountered the geo-feature: generating by the processor, an outputmessage comprising a select one of: a first message where a currentoperating state of the industrial vehicle is within a designatedacceptable range of an expected operating state, and a second messagedifferent from the first message, where the current operating state isoutside the designated acceptable range of the expected operating state;and conveying the output message on the industrial vehicle.
 2. Theprocess of claim 1, wherein: electronically receiving by a processor onan industrial vehicle, geo-feature information about a geo-feature thatis located in an area upon which the industrial vehicle travelscomprises: obtaining geo-feature information when a geo-feature isenabled, the geo-feature being enabled or disabled based upon the timeof day, the state of processes in various warehouse operational domains,or a combination thereof.
 3. The process of claim 1, wherein:electronically receiving by a processor on an industrial vehicle,geo-feature information about a geo-feature that is located in an areaupon which the industrial vehicle travels comprises: obtaininggeo-feature information when a geo-feature is enabled, the geo-featurebeing enabled or disabled based upon the type of industrial vehicle, theoperator, an operating condition of the industrial vehicle uponencountering the geo-feature, or a combination thereof.
 4. The processof claim 1, wherein: electronically receiving by a processor on anindustrial vehicle, geo-feature information about a geo-feature that islocated in an area upon which the industrial vehicle travels comprises:obtaining geo-feature information when a geo-feature is enabled, thegeo-feature being enabled or disabled based upon a productivity metric,the productivity metric determined by tracking a target number ofpallets or cases moved, a distance and route traveled per pick, a targetper specific idle segment, a target for the operator being off thevehicle, accuracy of correct pick or put location, or a combinationthereof.
 5. The process of claim 1, wherein: electronically receiving bya processor on an industrial vehicle, geo-feature information about ageo-feature that is located in an area upon which the industrial vehicletravels comprises: obtaining geo-feature information when a geo-featureis enabled, the geo-feature being enabled or disabled based upon adetermination that a travel area is congested.
 6. The process of claim1, wherein: detecting that the industrial vehicle has encountered thegeo-feature comprises detecting that the industrial vehicle hasencountered multiple, layered geo-features, wherein the industrialvehicle responds to each detected geo-feature in the layer.
 7. Theprocess of claim 6, wherein: a first one of the encountered multiple,layered geo-features comprises a message zone that prompts theindustrial vehicle to convey the output message, and a second one of theencountered multiple, layered geo-features comprises an action zone thatcauses the industrial vehicle to automatically make a change to anoperating parameter of the industrial vehicle while the industrialvehicle is in the action zone.
 8. The process of claim 1, wherein:conveying the output message on the industrial vehicle comprisesinitiating a light, display, prompt with a textual message, sound,speech based audible message, haptic response, or a combination thereof.9. The process of claim 1, wherein: conveying the output message on theindustrial vehicle comprises outputting the first message on a firstoutput device, and outputting the second message on a second outputdevice, the second output device being different from the first outputdevice.
 10. The process of claim 1, wherein: conveying the outputmessage on the industrial vehicle comprises wirelessly transmitting theoutput message across a short-range wireless connection to an electronicdevice of a pedestrian within a predefined range of the industrialvehicle.
 11. The process of claim 1, wherein: the industrial vehiclecomprises a first light visible to an interior of the industrial vehicleand a second light visible to an exterior of the industrial vehicle; andconveying the output message on the industrial vehicle comprisesactivating at least one of the first light and the second light of theindustrial vehicle upon outputting the output message.
 12. The processof claim 1 further comprising: implementing an operational controlresponsive to detecting the geo-feature, comprising automaticallyimplementing a modification to a vehicle operational parameter to set aspeed limit, force a travel direction, limit the maximum fork height, ora combination thereof.
 13. The process of claim 1 further comprising:detecting that the geo-feature is a restriction zone; and implementingan operational control responsive to detecting the geo-feature to causethe industrial vehicle to avoid the restriction zone.
 14. The process ofclaim 1 further comprising: initiating a process to set a window aroundrecorded events to encapsulate a record of an industrial vehicleencounter with the geo-feature, wherein: the record captures while theindustrial vehicle is in a zone defined by the encountered geo-featurevehicle speed, travel direction, fork height, weight on forks, operatorID, time of day, task being performed, message(s) received from thegeo-feature, a response/reaction to a received message, or a combinationthereof.
 15. A machine-executable process in an industrial vehicleenvironment, comprising: detecting that an industrial vehicle hasencountered a geo-feature designated as an aisle restriction zone; andperforming, upon detecting that the industrial vehicle has encounteredthe geo-feature: extracting from a warehouse management system computer,task information indicating whether the industrial vehicle is assigned atask to maneuver a load in an aisle associated with the aislerestriction zone; and generating a command that controls the industrialvehicle, comprising a select one of: a first command that restricts theindustrial vehicle from entering the aisle where the industrial vehicleis not assigned a task to maneuver a load in the aisle; and a secondcommand that enables the industrial vehicle to enter the aisle where theindustrial vehicle is assigned a task to maneuver a load in the aisle.16. The process of claim 15 further comprising: extracting from theindustrial vehicle, a current operating state; and generating the secondcommand where the industrial vehicle is assigned a task to maneuver aload in the aisle, and the extracted current operating state of theindustrial vehicle satisfies an expected operating state of theindustrial vehicle obtained from the aisle restriction zone geo-feature.17. The process of claim 16, wherein: the expected operating state ofthe industrial vehicle is obtained from the aisle restriction zonegeo-feature; and the expected operating state of the industrial vehiclecomprises a requirement that the industrial vehicle is traveling at aspeed below a predetermined speed limit.
 18. A machine-executableprocess in an industrial vehicle environment, comprising: obtaininggeo-feature information about geo-features that are located in an areaupon which an industrial vehicle travels; outputting to a display on theindustrial vehicle, a view that represents the area upon which theindustrial vehicle is traveling; visually indicating on the display, alocation of detected geo-features within the view of the display;detecting that the industrial vehicle has encountered a selectgeo-feature; and performing, upon detecting that the industrial vehiclehas encountered the select geo-feature, a corresponding action on theindustrial vehicle, where the corresponding action is determined basedupon the identity of the select geo-feature.
 19. The process of claim18, wherein: performing the corresponding action further comprisesdetermining the action based upon an operating state of the industrialvehicle.
 20. The process of claim 18 further comprising: interactingwith the display to create and deploy a new geo-feature with regard to alocation within the area upon which the industrial vehicle travels,around the industrial vehicle itself, or both.